Labels:text | menu | screenshot | document OCR: Table A. Definitions of Key Productivity Factors* Productivity factor Very low [1] Low (2) Nominal [3] High (4) Very high (5) Customes participa- Passive; chert defines Ciest delints or Active: client defines lion (P01) or approves < 30% of appruws 20-70% cf or approves > 70% of Very active the functions the functions the most important participation funcions. Statt availability Big problems in key Mergers involves Key members are Members of project Qualhied software (P03 software personnel in other projects involved in only one are involved almost availability, sothevare simultaneously and other project full fine personnel are avall- requires specialized able when needed have maintenance and can participate knowledge responsibilities fully in project Standards use (PO4) Project managers Some standards are Project members Project members use Quality of standards must donclop stan- Project members use available, but not use generally known new standards, which new standards, which applied in the project dards during project familiar, project man- standards in known other customers of aren't famisar in the agers must develop environments software houses have `dusty. but must be more applied in the same loTowed, use is environment controlled TODIS USB (PD5) Animal tools: edi- Basic tools; inter- Development envi- Modent tools ske tors, compilers, test- Integralcd CASE preters, ed tors, com- ronmem, DBMS, CASE, project plan- environment covers ing tools pilers, debuggers, support for most databases, libraries ring, application gen- entire ffccyclepal phases erators, standardized todis cap support interfaces between each other flexibly chases Logical complexity Only routines: no Functionally clear: no Functionaly typical: Processing more de- Functionally and (F47) Computing, UD need for user inter- a gor thmic tasks; normal standard manding, database technically difficult needs, and user inter face: simple database solution database: no large and complex; solutiont; user inter- face requirements database clear algorithms new requirements for face very complex user interfaces distributed database Requirements No new features: Some changes to More changes to Some major changes, volatility (P05] Continuously new Standard compo- specifications; Some spoufications, but Impacting total archi- requirements; lots of nents: conversions new or adapted fung- project members can tecture and requiring rework; > 30% of tions; some minor hang c " em, and their rework: 15-3065 of the functions new of Changes in cala impact is minor functions new or mod hed comments (< 15% new or modi- modied fed tuctions) Efficiency require- No elliciency require- Efficiency goals maisy Capacity level of the Specific peaks in Efficiency is essent al. ments (210) ments needing aben- to reach, require- software is stable and capacity, response strict efficiency goals tion and planning ments celow average pres ctable. zesporse time, transaction pro- need continuo.s time, transaction atention and specific load, and turmround around time can be skils time are typical reached by specific design and implemen- lation techniques Staff tool skills c 8 months 6 -12 montt5 1-3 years 3-6 years > 6 years experience (P14) Average pro- experience jetteteam experience
(2000).iso/ieees/011/maxwt10a.gif){kind=small}
(2000).iso/ieees/011/hantt102.gif){kind=link}